Date: Tue, 16 Aug 94 04:30:02 PDT From: Advanced Amateur Radio Networking Group Errors-To: TCP-Group-Errors@UCSD.Edu Reply-To: TCP-Group@UCSD.Edu Precedence: Bulk Subject: TCP-Group Digest V94 #174 To: tcp-group-digest TCP-Group Digest Tue, 16 Aug 94 Volume 94 : Issue 174 Today's Topics: another dama trace dial on jnos110f (5 msgs) Linux and AX.25 (3 msgs) Linux compile failures - help??? (2 msgs) Okie Thoughts #1 Okie Thoughts #2 (3 msgs) Send Replies or notes for publication to: . Subscription requests to . Problems you can't solve otherwise to brian@ucsd.edu. Archives of past issues of the TCP-Group Digest are available (by FTP only) from UCSD.Edu in directory "mailarchives". We trust that readers are intelligent enough to realize that all text herein consists of personal comments and does not represent the official policies or positions of any party. Your mileage may vary. So there. ---------------------------------------------------------------------- Date: Tue, 16 Aug 94 11:56:29 EST From: BARRY TITMARSH Subject: another dama trace To: TCP-GROUP , wnos-group This trace comes from another Authors implementation of DAMA_SLAVE this time into wampes code. again the trace shows a data frame being sent in responce to a DAMA UA(F) received, this is the same type implementation as I have done into wnos-940815 I need some advive or comments on the DAMA spec. Local sysops who run a dama digi say that info frames should not be sent untill the slave system is polled again IE RR(P)+dama this will slow doen tcpip even more, and tcpip over a dama digi is 10 times as slow, comapired to a notmal ax25 VC mode. Come on please some comments. I need some help. what to do.! Barry. gm8sau/dc0hk Mon Aug 15 09:28:57 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG SABM(P) Mon Aug 15 09:29:33 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG SABM(P) Mon Aug 15 09:29:39 1994 - ttyS1 recv: KISS: crc-16 Data AX25: ¦DAMAá DB0PRA-6->DD8NE v DB0BBG* UA(F) Mon Aug 15 09:29:39 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG I NR=0 NS=0 pid=IP IP: len 84 dd8ne-gate.ampr.org->db0pra.ampr.org ihl 20 ttl 19 prot ICMP ICMP: type Echo Request id 0 seq 0 0000 9.O..................... !"#$%&'()*+,-./0123456789:;<=>? Mon Aug 15 09:29:42 1994 - ttyS1 recv: KISS: crc-16 Data AX25: ¦DAMAá DB0PRA-6->DD8NE v DB0BBG* RR(P) NR=1 Mon Aug 15 09:29:42 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG RR(F) NR=0 Mon Aug 15 09:30:12 1994 - ttyS1 recv: KISS: crc-16 Data AX25: ¦DAMAá DB0PRA-6->DD8NE v DB0BBG* I(P) NR=1 NS=0 pid=IP IP: len 84 db0pra.ampr.org->dd8ne-gate.ampr.org ihl 20 ttl 15 prot ICMP ICMP: type Echo Reply id 0 seq 0 0000 9.O..................... !"#$%&'()*+,-./0123456789:;<=>? Mon Aug 15 09:30:12 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG RR(F) NR=1 Mon Aug 15 09:30:34 1994 - ttyS1 recv: KISS: crc-16 Data AX25: ¦DAMAá DB0PRA-6->DD8NE v DB0BBG* RR(P) NR=1 Mon Aug 15 09:30:34 1994 - ttyS1 sent: KISS: crc-16 Data AX25: DD8NE->DB0PRA-6 v DB0BBG RR(F) NR=1 ------------------------------ Date: Mon, 15 Aug 1994 10:04:40 -0600 (MDT) From: Klarsen Subject: dial on jnos110f To: brian@lantz.cftnet.com Brian thank you for your very infomative but totally un-readable file. I am somewhat of a linguest but it looks not like any language I have ever seen. Further, if you plan on sending me dialer.c please save your time since I have that in english already. -karl ------------------------------ Date: Mon, 15 Aug 1994 10:50:51 -0700 From: myers@bigboy73.West.Sun.COM (Dana Myers ) Subject: dial on jnos110f To: klarsen@kazak.NMSU.Edu Karl Larsen wrote: > From: Klarsen > Subject: dial on jnos110f > To: brian@lantz.cftnet.com > Cc: TCP digest > Mime-Version: 1.0 > > > Brian thank you for your very infomative but totally un-readable > file. I am somewhat of a linguest but it looks not like any language I > have ever seen. > > Further, if you plan on sending me dialer.c please save your time > since I have that in english already. > > -karl What's with the snide tone of this reply? Oh well, here's a un-uuencoded version of the file: -------Start of included text------------- control down wait 2000 control up speed 9600 send "atz\ratm0l0\r" wait 1000 send "atdtd555-5555\r" wait 45000 "CONNECT" wait 15000 "ogin" wait 1000 send "myname\r" wait 5000 "assword" wait 1000 send "mypassword\r" wait 120000 ------End of included text-------------- ------------------------------ Date: Mon, 15 Aug 1994 16:14:14 -0600 (MDT) From: Klarsen Subject: dial on jnos110f To: Dana Myers On Mon, 15 Aug 1994, Dana Myers wrote: > Karl Larsen wrote: > > From: Klarsen > > Subject: dial on jnos110f > > To: brian@lantz.cftnet.com > > Cc: TCP digest > > Mime-Version: 1.0 > > > > > > Brian thank you for your very infomative but totally un-readable > > file. I am somewhat of a linguest but it looks not like any language I > > have ever seen. > > > > Further, if you plan on sending me dialer.c please save your time > > since I have that in english already. > > > > -karl > > What's with the snide tone of this reply? > > Oh well, here's a un-uuencoded version of the file: > > -------Start of included text------------- > control down > wait 2000 > control up > speed 9600 > send "atz\ratm0l0\r" > wait 1000 > send "atdtd555-5555\r" > wait 45000 "CONNECT" > wait 15000 "ogin" > wait 1000 > send "myname\r" > wait 5000 "assword" > wait 1000 > send "mypassword\r" > wait 120000 > ------End of included text-------------- > OK I did read this fine and it looks EXACTLY like that I used with net.exe of 1989 vintage. I will try it again and in all probability re-compile jnos to make sure it isn't the problem. Now, I DID read dialer.c and it DOES say that it has been re-written to make it " more human understandable" and that always tends to make me worry. All this re-write was done in 1991 so it's been around a good while. If I sounded snide, it was because I was trying to be snide. When a person asks for help, and it arrives in a language you have never seen it IS an unhappy event. ------------------------------ Date: Mon, 15 Aug 1994 16:31:04 -0700 From: myers@bigboy73.West.Sun.COM (Dana Myers ) Subject: dial on jnos110f To: tcp-group@UCSD.EDU > Date: Mon, 15 Aug 1994 16:14:14 -0600 (MDT) > From: Klarsen > Subject: Re: dial on jnos110f > If I sounded snide, it was because I was trying to be snide. When > a person asks for help, and it arrives in a language you have never seen > it IS an unhappy event. Well, that's too bad. When you ask for help, and someone tries, in good faith, to help you, free of charge, and doesn't quite give you what you need, it isn't really proper to become snide. After all, even well intentioned people sometimes make mistakes. A polite "what is this?" note sent privately to the sender would probably have resulted in him sending the file in form you could deal with. As it is, I wouldn't blame him if he didn't offer you help in the future, and many other people may be apprehensive to help you, too. Of course, we all need to be careful about using mail interface features not found in all mail programs, like attachments. ------------------------------ Date: Mon, 15 Aug 1994 19:59:25 +0100 From: "Brian A. Lantz" Subject: dial on jnos110f To: tcp-group@UCSD.EDU On Mon, 15 Aug 1994, Dana Myers wrote: > Karl Larsen wrote: > > > > Brian thank you for your very infomative but totally un-readable > > file. I am somewhat of a linguest but it looks not like any language I > > have ever seen. > > > > Further, if you plan on sending me dialer.c please save your time > > since I have that in english already. > > > > -karl > > What's with the snide tone of this reply? > > Oh well, here's a un-uuencoded version of the file: I'm sorry! PARDON ME, for using Internet MIME format in a message to TCP-GROUP!! I won't let it happen again! I, too, am wondering about the "snide tone"! Just tried to help (that was my mistake, obviously).... ----------------------------------------------------------- Brian A. Lantz/KO4KS brian@lantz.cftnet.com REAL PORTION of Microsoft Windows code: while (memory_available) { eat_major_portion_of_memory (no_real_reason); if (feel_like_it) make_user_THINK (this_is_an_OS); gates_bank_balance++; } ------------------------------ Date: Tue, 16 Aug 94 08:22:21 EST From: terry@orac.dn.itg.telecom.com.au (Terry Dawson) Subject: Linux and AX.25 To: srbible@cs.nps.navy.mil, tcp-group@UCSD.EDU >Some errata to Terry Dawson's NET-2/3 HOWTO. > >1. p.53 - krnl022.tgz should read ax25krnl.tgz > - user022.tgz should read ax25util.tgz > - need to add a section explaining how to apply patches to > the ax25 kernel code. Ta, I'll fix that. >2. p.54 - the example # gzip -dc user022.tgz | tar xvvof - > is this right? ^^^^^ (?xvf?) six of one, half dozen of the other. slightly different options. >3. p.12 - /pub/misc/Linux/Networking/... should read > /pub/Linux/Networking/... (two places) Alan was still rearranging sunacm when I wrote it. I will need to update all of the directories specified. >7. I did try Linux+AX25 on the local 2 meter frequency using a > PACCOMM TNC-200 in KISS mode. I was able to 'call' and 'ftp' > to the local MSYS BBS which is setup for TCP/IP. But when I > tried to telnet, MSYS would ask for my callsign, I typed it in > and MSYS simply disconnected me. I can telnet to the MSYS BBS > using JNOS, proving to me that the BBS end is working (?). > I'm wondering what Linux+AX25 is doing to cause this? MSYS, blerk. Yu'll probably find that you have to ask the MSYS sysop to add you to a list of known tcp/ip nodes. That's what I had to do here for an MSYS node. >Is there a need for a HOWTO to set all of this up (Alan mentioned this in >AX25017/INSTALL.TXT)? The NET-2 HOWTO guide gives a good overview of what >needs to be done, but my biggest problem was figuring out what was the >latest code, code versions that required other versions, etc. I first >gathered up all the HOWTOs, READMEs, man pages, etc. and correlated all the >information. Not all of it matched. I downloaded and used the latest code >I code find (see above). Good question. I'm hoping to expand the AX.25 section in the NET-2-HOWTO. But I could probably do that endlessly. I wonder if it is worth creating a NET-3-AX25-HOWTO ? I might add a section describing a 'typical' amateur scenario. Including sample files and the like. >I have ordered two Ottawa PI2 cards. As soon as those arrive I will be >integrating them into the system. Good cards. thanks for the feedback regards Terry ------------------------------ Date: Mon, 15 Aug 1994 21:20:40 -0400 From: "Brandon S. Allbery" Subject: Linux and AX.25 To: terry@orac.dn.itg.telecom.com.au (Terry Dawson) In your message of Tue, 16 Aug 1994 08:22:21 EST, you write: +--------------- | MSYS, blerk. Yu'll probably find that you have to ask the MSYS sysop to | add you to a list of known tcp/ip nodes. That's what I had to do here for | an MSYS node. +------------->8 Don't blame Mike for that one; he got hounded by a local sysop who thinks TCP/IP is the Black Plague and *DEMANDED* in no uncertain terms that TCP/IP be blocked in the default case or he'd stop supporting MSYS development. Since said sysop is one of Mike's biggest supporters/helpers, Mike had little choice but to do it. ++Brandon -- Brandon S. Allbery KF8NH [44.70.4.88] bsa@kf8nh.wariat.org Linux development: iBCS2, JNOS, MH ------------------------------ Date: Tue, 16 Aug 1994 15:03:33 +1000 (EST) From: Dave Horsfall Subject: Linux and AX.25 To: tcp-group@ucsd.edu On Mon, 15 Aug 1994, Brandon S. Allbery wrote: | Don't blame Mike for that one; he got hounded by a local sysop who | thinks TCP/IP is the Black Plague and *DEMANDED* in no uncertain terms | that TCP/IP be blocked in the default case or he'd stop supporting MSYS | development. Since said sysop is one of Mike's biggest | supporters/helpers, Mike had little choice but to do it. Sounds like an excellent reason to encourage people to stop using MSYS. Evolution in action, and all that... -- Dave Horsfall (VK2KFU) | dave@esi.com.au | VK2KFU @ VK2AAB.NSW.AUS.OC | PGP 2.6 Opinions expressed are mine. | E7 FE 97 88 E5 02 3C AE 9C 8C 54 5B 9A D4 A0 CD ------------------------------ Date: Tue, 16 Aug 1994 09:08:25 +1200 From: D.N.Muir@massey.ac.nz (Dexter Muir) Subject: Linux compile failures - help??? To: TCP-Group@ucsd.edu Greetings, all... I am somewhat of a 'newbie' to Linux, and am experiencing some difficulties which I could not find documented (perhaps I look in the wrong places??? :-) Firstly, a brief description of my hardware: 486dx-33, 8MB DRAM, 256kB cache, 80 and 100MB IDE H/D's, 1.44 F/D 80MB disk used for messy-dos as C: 100MB for Linux, 12 as swap (/dev/hdb1, formatted with mkswap and enabled with swapon). Linux is slackware 1.2.0, from sunsite.unc.edu I am attempting to re-compile the kernel with SCC drivers. Firstly, I tried compiling a small utility (the 'mouseless commander' - very useful!). make clean would work fine, but that's only removing old scraps. make dep would fail occasionally with a file or path not found ( at all sorts of random points in the process ), though a manual check with ls would find nothing amiss. make would fail with a message: Program cc1 got fatal signal 11 ( once again at all sorts of random points in the process ), then exit and close pipes. It looked like a memory-type problem, with failure occurring at all stages, so I tried disabling swap and relying on RAM. Disabling swap with 'swapoff -a' cured this - a clean compile! Next I attempted a re-compile of the kernel. With swap space enabled, I could not always get through make dep. If I did, make bombed out (as above) very early. With swap disabled, make dep was reliable, and I got further into make, but eventually the same bomb-out. Failing this, I thought I'd try compiling a version of NOS (alpha4). This also failed, in similar fashion, then came a message: segmentation error That's as far as I got - make keeps coming up with this error whether swap is on or off (I suspect either RAM or the main partition, though fsck reports no problems). Does anyone have any pointers / advice? I'm stuck! Dexter N. Muir Manufacturing Pilot Plant Technician D.N.Muir@massey.ac.nz Department of Production Technology Massey University, Palmerston North, New Zealand ------------------------------ Date: Tue, 16 Aug 94 13:56:48 EST From: terry@orac.dn.itg.telecom.com.au (Terry Dawson) Subject: Linux compile failures - help??? To: D.N.Muir@massey.ac.nz, TCP-Group@UCSD.EDU > I am somewhat of a 'newbie' to Linux, and am experiencing some >difficulties which I could not find documented (perhaps I look in the wrong >places??? :-) You probably should carry this thread to one of the Linux specific mailing lists, or newsgroups. > make would fail with a message: > Program cc1 got fatal signal 11 ( once again at all sorts of >random points in the process ), then exit and close pipes. Sounds like you don't have your swap configured correctly as you may have already deduced. Again, this would be better addressed in a linux specific area. regards Terry ------------------------------ Date: Mon, 15 Aug 1994 18:22:24 -0500 (CDT) From: ssampson@sabea-oc.af.mil (Steve Sampson) Subject: Okie Thoughts #1 To: tcp-group@ucsd.edu I downloaded WNOS. I tried to compile it. What a mess... How about taking the JNOS Makefile and reading it, then maybe taking notes and implementing a new WNOS Makefile. The one that comes with the archive is a piece of shit. Thanks, -- Steve ------------------------------ Date: Mon, 15 Aug 1994 18:23:43 -0500 (CDT) From: ssampson@sabea-oc.af.mil (Steve Sampson) Subject: Okie Thoughts #2 To: tcp-group@ucsd.edu Brian A. Lantz writes: > This message is in MIME format. The first part should be readable text, > while the remaining parts are likely unreadable without MIME-aware tools. Seems like you had to go through a lot of trouble to make that contribution unreadable. What's wrong with plain ASCII text? Sheesh... -- Steve ------------------------------ Date: Mon, 15 Aug 1994 21:49:47 +0100 From: "Brian A. Lantz" Subject: Okie Thoughts #2 To: Steve Sampson On Mon, 15 Aug 1994, Steve Sampson wrote: > > Brian A. Lantz writes: > > This message is in MIME format. The first part should be readable text, > > while the remaining parts are likely unreadable without MIME-aware tools. > > Seems like you had to go through a lot of trouble to make that contribution > unreadable. What's wrong with plain ASCII text? Sheesh... I DIDN'T go to a lot of trouble. It is a standard part of my mailer. Once again, I AM VERY SORRY for trying to help! Judging from the plain out and out RUDE treatment I got from this attempt and the attitude that I received from using STANDARD Internet tools, I don't believe I will be offering any assistance in this mailing list again! Thanks! ----------------------------------------------------------- Brian A. Lantz/KO4KS brian@lantz.cftnet.com REAL PORTION of Microsoft Windows code: while (memory_available) { eat_major_portion_of_memory (no_real_reason); if (feel_like_it) make_user_THINK (this_is_an_OS); gates_bank_balance++; } ------------------------------ Date: Mon, 15 Aug 1994 21:54:05 +0100 From: "Brian A. Lantz" Subject: Okie Thoughts #2 To: Steve Sampson On Mon, 15 Aug 1994, Steve Sampson wrote: But before I go into the shadows, the message quoted here, is SAID to be a quote from me. I never wrote this message, and am wondering why I am being attributed with a message, in order to be FLAMED. Now, not only am I getting flamed, but I am getting it for messages I haven't even written. Come on, guys! GET A LIFE! And leave MINE alone! > Brian A. Lantz writes: > > This message is in MIME format. The first part should be readable text, > > while the remaining parts are likely unreadable without MIME-aware tools. > > Seems like you had to go through a lot of trouble to make that contribution > unreadable. What's wrong with plain ASCII text? Sheesh... > -- > Steve > ----------------------------------------------------------- Brian A. Lantz/KO4KS brian@lantz.cftnet.com REAL PORTION of Microsoft Windows code: while (memory_available) { eat_major_portion_of_memory (no_real_reason); if (feel_like_it) make_user_THINK (this_is_an_OS); gates_bank_balance++; } ------------------------------ End of TCP-Group Digest V94 #174 ******************************